Reminder service for email selected for follow-up actions

ABSTRACT

An apparatus and method of operating a computer system is disclosed herein for rendering a user interface of an email service that includes a triage menu. In a user interface to an email service, an option to triage an email is rendered. In response to a selection of the option to triage the email, a triage menu is rendered that comprises a plurality of triage actions. At least one triage action of the plurality of triage actions corresponds to a service other than the email service. In response to a selection of the one triage action, triage information is communicated which indicates the selection of the one triage action to trigger a reminder in an application associated with the service.

RELATED APPLICATIONS

This divisional application claims the benefit of, and priority to, U.S.patent application Ser. No. 14/150,114, entitled “Reminder Service forEmail Selected for Follow-up Actions”, filed on Jan. 8, 2014, which ishereby incorporated by reference in its entirety for all purposes.

TECHNICAL FIELD

Aspects of the disclosure are related to computing hardware and softwaretechnology, and in particular to a reminder service for email.

TECHNICAL BACKGROUND

Email triage is an exercise engaged in by email users in order toorganize messages in their inbox or other folders. When triaging theiremail, users make quick decisions about how to handle a given email,such as by electing to delete an email, move an email to another folder,or mark an email for later follow up.

Some email applications provide specific features to assist with triage,such as the follow-up feature in Microsoft® Outlook® that allows a userto mark an email for follow up later that day, the next day, or even ina matter of weeks or more. A task is then scheduled in the task module,a reminder can be set for the task, and so on.

Users frequently user their mobile devices to triage email. Mobilesituations tend to lend themselves to brief interactions with one'sinbox, such as when traveling or at other moments when there is enoughtime to make some decisions with respect to an email, but not enoughtime to prepare a detailed response or otherwise respond at length.

Many mobile email applications lack some of the features andfunctionality as their desktop counterparts, and thus may not offertriaging capabilities. In such situations, users sometimes resort toad-hoc solutions to triage their email, such as by marking read messagesas “un-read” so as to capture their attention later. At the very least,some limited triage is possible by deleting messages, but this islargely a sub-optimal experience.

However, one solution supports email triage in a mobile environment byproviding a triage view of a user's mail in terms of those messages thathave been triaged and those that remain un-triaged. The user cannavigate to the triaged emails or possibly to the un-triaged emails.When dealing with the un-triaged emails, the user can elect an email tobe handled next or deferred for later reference. A specific task canalso be created in association with an email, such as to place a call orschedule a meeting related to the email.

As a user progresses through their email, various tasks will be createdwhich can then be viewed later by way of a desktop email client. Inaddition to viewing their inbox, a user may view their tasks in thedesktop email client, organized in various ways, such as by the tasktype or by when the tasks are due.

Overview

Provided herein are systems, methods, and software for rendering a userinterface that includes a triage menu through which to select an optionto triage an email. In at least one implementation, a triage menu isrendered that comprises a plurality of triage actions in response to aselection of the option to triage the email. At least one triage actionof the plurality of triage actions corresponds to a service other thanthe email service. In response to a selection of the one triage action,triage information is communicated which indicates the selection of theone triage action to trigger a reminder in an application associatedwith the service.

In some implementations, a user interface includes a view of a pluralityof emails. Along with the plurality of emails, a plurality of filterscorresponding to a number of follow-up actions may also be includedwhere each filter corresponds to an associated follow-up action. When afilter is selected, the display system renders the emails thatcorrespond to the follow-up actions associated with the filter.

In other implementations, the follow-up actions are associated withadditional applications to carry out the function specified by thefollow-up action. The follow-up actions may be manually, automatically,or programmatically associated with the additional applications.

This Overview is provided to introduce a selection of concepts in asimplified form that are further described below in the TechnicalDisclosure. It may be understood that this Overview is not intended toidentify key features or essential features of the claimed subjectmatter, nor is it intended to be used to limit the scope of the claimedsubject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the disclosure can be better understood with referenceto the following drawings. While several implementations are describedin connection with these drawings, the disclosure is not limited to theimplementations disclosed herein. On the contrary, the intent is tocover all alternatives, modifications, and equivalents.

FIG. 1 illustrates an operational scenario in an implementation.

FIG. 2 illustrates a triage process in an implementation.

FIG. 3 illustrates a triage process in an implementation.

FIG. 4 illustrates a triage process in an implementation.

FIG. 5A illustrates an operational scenario in an implementation.

FIG. 5B illustrates an operational scenario in an implementation.

FIG. 6 illustrates a user interface to an email application and anassociated operational scenario in an implementation.

FIG. 7 illustrates an operational scenario in an implementation.

FIG. 8 illustrates an operational scenario in an implementation.

FIG. 9 illustrates a computing system in an implementation.

TECHNICAL DISCLOSURE

Implementations disclosed herein refer to a reminder service forenhancing email triage. When engaged with an email application, a usermay select an email for a follow-up action. When engaged later withanother application, such as another email client, a productivityapplication, a contacts application, or a game, for example, the usermay be reminded of the email and the follow-up action. In this manner,awareness of email that is triaged using one application is not lost ordissipated when engaged with other applications.

In at least one implementation, a reminder service receives actioninformation indicative of an email selected for follow-up action in anemail application and responsively identifies an additional applicationthrough which to surface a reminder about the follow-up action. Thereminder service communicates reminder information to the additionalapplication with which to render the reminder.

In some scenarios, the additional application may be selected fromvarious other applications based at least in part on with which of theapplications the follow-up action is associated. Examples of the otherapplications include, but are not limited to, a real-time communicationapplication, a contacts application, a calendar application, aproductivity application, and an additional email application. Examplesof follow-up actions include reading the email later, replying to theemail later, placing a call related to the email later, and scheduling ameeting related to the email later.

The follow-up action may be selectable in some implementations from atriage menu in the email application. The applications may be associatedwith the various follow-up actions such that, in at least one scenario,the follow-up action is associated with an additional email applicationand at least one other application. The additional application may be,for instance, a contacts application, in which case a reminder may berendered in a user interface to the contacts application. The remindermay even be rendered in visual association with one of various contactsincluded in the user interface. In other instances, the additionalapplication may be a productivity application, in which case thereminder may be rendered in a user interface to the productivityapplication. For example, the reminder may be included in a mostrecently used (M.R.U.) menu in visual association with a documentrepresented in the most recently used menu.

Referring now the drawings, FIG. 1 illustrates an operational scenarioin an implementation in which an email application and additionalapplications interact with a reminder service. FIGS. 2-4 illustratestriage processes employed by the email application, the reminderservice, and the additional applications. FIG. 5A and FIG. 5B illustratetwo more operational scenarios. FIG. 6 illustrates a user interface toan email application in an operational scenario, as does FIG. 7. FIG. 8illustrates a user interface to a contacts application and a userinterface to a productivity application. FIG. 9 illustrates a computingsystem representative of any apparatus, device, or collections thereofsuitable for implementing a reminder service, an email application, oran additional application, and for implementing the various operationalscenarios disclosed herein.

In operational scenario 100 illustrated in FIG. 1, an email application110 is in communication with a reminder service 115 to facilitateenhanced email triage. Reminder service 115 may also be in communicationwith an additional application 120 and another additional application130.

Email application 110 is representative of any software application,module, component, or collections thereof for conducting email, withwhich a user may engage in order to obtain access to and interact withan email service (not shown). Email application 110 is capable ofemploying triage process 200, described in more detail below withrespect to FIG. 2. Various types of physical or virtual computingsystems may be used to implement email application 110, such as servercomputers, desktop computers, laptop computers, tablet computers, smartphones, gaming appliances, or any other suitable computing appliance, ofwhich computing system 900, discussed below with respect to FIG. 9, isrepresentative. Email application 110 may be locally installed andexecuted, executed from within the context of a browser, streamed, orotherwise delivered in some other suitable manner, includingcombinations or variations thereof.

Reminder service 115 is representative of any software application,module, component, or collections thereof capable employing triageprocess 300 in support of triage decisions made with respect to emailapplication 110. Reminder service 115 may be implemented in astand-alone fashion or may be implemented within other environments inan integrated or cooperative fashion.

Various types of physical or virtual computing systems may be used toimplement triage process 300 within the context of reminder service 115,such as server computers, desktop computers, laptop computers, tabletcomputers, smart phones, or any other suitable computing appliance, ofwhich computing system 900, discussed below with respect to FIG. 9, isrepresentative. When implemented using a server computer, any of avariety of servers may be used including, but not limited to,application servers, database servers, mail servers, rack servers, bladeservers, tower servers, or any other type of server, variation orcombination thereof.

Additional application 120 is representative of any softwareapplication, module, component, or collection thereof, capable ofrendering a reminder about an email selected for triage. Examples ofadditional application 120 include, but are not limited to, productivityapplications, contact applications, calendar applications, games, andemail applications, as well as any other type of application. Additionalapplication 130 is also representative of such applications. Bothadditional application 120 and additional application 130 are capable ofemploying triage process 400 to facilitate enhanced triage. Varioustypes of physical or virtual computing systems may be used to implementadditional application 120 and additional application 130, such asserver computers, desktop computers, laptop computers, tablet computers,smart phones, gaming appliances, or any other suitable computingappliance, of which computing system 900, discussed below with respectto FIG. 9, is representative. Additional application 120 and additionalapplication 130 may be locally installed and executed, executed withinthe context of a browser, streamed, or otherwise delivered in some othersuitable manner.

In operational scenario 100, a user interacts with email application 110through user interface 111, which is a user interface to an emailservice. For example, a user may interact with their email, compose orread messages, move and sort messages, or otherwise perform any numberof actions using user interface 111.

User interface 111 includes a list of emails representative of those auser may encounter in an inbox, or some other folder, including email112, email 113, and email 114. It may be appreciated that other elementsare possible, in place of or in addition to those included in userinterface 111, and may be considered within the scope of the presentdisclosure. It is assumed for exemplary purposes that email 113 has beenselected for triaging, as indicated by its shaded representation.

In addition, a triage menu 118 has been selected or otherwise surfaced,which includes follow-up actions 116 selectable from the triage menu118. A user input 117 or selection is made from the triage menu 118 ofone of the follow-up actions 116, in response to which actioninformation is communicated by email application 110 to reminder service115. The action information identifies the email (or emails) and thefollow-up action.

Reminder service 115 receives the action information and responsivelyidentifies which additional application corresponds to the follow-upaction identified in the action information. In this scenario, it isassumed for exemplary purposes that additional application 120corresponds to the follow-up action. Accordingly, reminder service 115communicates reminder information to additional application 120indicative of the follow-up action and the email. Optionally, reminderservice 115 may also communicate reminder information to additionalapplication 130.

Additional application 120 receives the reminder information andpresents it in user interface 121. User interface 121 includes interfaceelement 122 and interface element 123, which are representative of anygraphical elements, or any other type of element, that may beencountered in a user interface. A reminder 124 is rendered in userinterface 121 such that a user may be reminded of the email and thefollow-up action when interacting with interface elements in userinterface 121. Reminder 124 is positioned in visual association withinterface element 122 for exemplary purposes, although it may beappreciated that it may be arranged visually in user interface 121 inany other way.

FIG. 2 illustrates triage process 200 which may be employed by emailapplication 110 within the context of operational scenario 100, althoughit may be appreciated that triage process 300 could be employed in otherscenarios. In operation, email application 110 renders a visualrepresentation of follow-up actions (step 201). While triage menu is anexample of a drop-down menu, a variety of other menus or other ways inwhich to present the follow-up actions from which a user may make aselection are possible and may be considered within the scope of thepresent disclosure.

Next, email application 110 receive a selection input by a user via userinterface 111 selecting a particular email or emails for triage andidentifying one of the follow-up actions from the presentation offollow-up actions (step 203). The selection may be made by, for example,a gesture, a touch, a mouse click, or some other suitable user input.

Upon receiving the selection(s) via user interface 111, emailapplication 110 communicates action information to reminder service 115indicative of the email or emails selected for triage and the associatedfollow-up action (step 205). Reminder service 115 may then handle theaction information in accordance with triage process 300.

FIG. 3 illustrates triage process 300 which may be employed by reminderservice 115 in the context of operational scenario 100, although it maybe appreciated that triage process 300 could be employed in otherscenarios. In operation, reminder service 115 receives actioninformation from an email application, such as email application 110(step 301). The action information identifies an email or emailsselected for triage and an associated follow-up action. Reminder service115 proceeds to identify which additional application or applications isassociated with the follow-up action and through which a reminder may besurface (step 303).

In an example, the follow-up action may be to call a person associatedwith the triaged email, in which case the additional applicationassociated with the follow-up action may be a dialer application, acontacts application, a voice calling application, or some otherapplication generally associated with placing calls. In another example,the triaged email may include an attachment and the follow-up action maybe to read the triaged email. The associated application may be a readerapplication or some other productivity application with which theattachment can be read. In yet another example, the follow-up action maybe to schedule an event, in which case the associated application may bea calendar application.

Such associations between additional applications and follow-up actionsmay be configured at any time. The associations may be configuredmanually, automatically, programmatically, or in some other manner. Thefollow-up actions may be associated with just one application but mayalso be associated with more than one application. The follow-up actionsare generally associated with applications based on a functionalrelationship between the actions and the applications. For instance, afollow-up action to place a call may be associated with one or moreapplications suitable for placing a call. However, other associationscan be made. Thus, an additional email application may be associatedwith any follow-up action so that reminders can be surfaced through theadditional email application, regardless of whether or not theadditional email application is suitable for performing the follow-upaction.

Having identified the appropriate additional application orapplications, reminder service 115 communicates reminder information tothe application or applications (step 305). Such communication may occurin a variety of ways, such in a push manner in which reminder service115 initiates communication with the additional application(s) in orderto transfer the reminder information. However, reminder service 115 mayalso be polled by the various applications on a periodic basis or someother basis. Other communication mechanisms are possible for conveyingreminder information and may be considered within the scope of thepresent disclosure.

FIG. 4 illustrates triage process 400 which may be employed by otherapplications, such as additional application 120 or additionalapplication 130, in the context of operational scenario 100, although itmay be appreciated that triage process 300 could be employed in otherscenarios. In operation, user interface 121 is invoked and presented byadditional application 120 (step 401). Before, during, or after whenuser interface 121 is invoked, additional application 120 receivesreminder information from reminder service 115 indicative of a triagedemail and an associated follow-up action (step 403).

The email and follow-up action may be identified directly in thereminder information. For instance, the reminder information mayspecifically identify the email by a name, a link, or some otheridentifier. The follow-up action may also be specifically identified bya name, a link, or some other identifier. However, the email and thefollow-up action may be identified indirectly by the reminderinformation. For instance, the reminder information may merely indicatein general that an email exists that has been triaged and that has anassociated follow-up action. Other ways of representing the email andthe follow-up action in reminder information are possible, in additionto or in place of those disclosed herein, and may be considered withinthe scope of the present disclosure.

Having received the reminder information, additional application 120renders a reminder in user interface 121 (step 405). The reminder may berepresented in text, as a graphical element, or in some other mannerthat serves to visually remind a user about a triaged email. In somescenarios, the reminder may be rendered as an email icon or image,although other types of images are possible, such as a star, colorcoding, font modifications, and the like.

FIG. 5A illustrates another operational scenario 501 in animplementation in which multiple additional applications are capable ofsurfacing reminders, including an email application 520, a contactsapplication 530, and a calendar application 540. In addition,operational scenario 501 involves a personal information service 512 inthe context of which a reminder service 515 may be implemented.

Examples of personal information service 512 include, but are notlimited to, Microsoft® Exchange®, Gmail®, and Yahoo! ® Mail, as well asany other suitable personal information service, variation, orcombination thereof. Reminder service 515 is representative of anysoftware service, application, module, component, or variations andcombinations thereof that may run within the context of personalinformation service 512. Personal information service 512 and reminderservice 515 may be implemented using any suitable computing system orcollection of computing systems, of which computing system 900illustrated in FIG. 9 is representative.

Email application 510 is representative of any email application,module, or component capable of communicating triage information. Emailapplication 520 is representative of any email application, module, orcomponent capable of receiving reminder information and surfacing areminder. Contacts application 530 is representative of any contactsapplication, module, or component capable of receiving reminderinformation and surfacing a reminder. Calendar application 540 isrepresentative of any calendar application, module, or component capableof receiving reminder information and surfacing a reminder.

Email application 510, email application 520, contacts application 530,and calendar application 540 may be implemented as separate applicationsor in an integrated fashion within the context of another application.In addition, email application 510, email application 520, contactsapplication 530, and calendar application 540 may be implemented on asingle device or on multiple, different devices. Any combination ofapplications and devices is also possible and may be considered withinthe scope of the present disclosure.

In operational scenario 501, an email is selected for follow-up actionand email application 510 communicates triage information indicative ofthe same to reminder service 515. The triage information may becommunicated directly to reminder service 515 or indirectly throughpersonal information service 512.

Reminder service 515 identifies which other applications are associatedwith the follow-up action indicated by the triage information andcommunicates reminder information to those applications about thetriaged email. In operational scenario 501, it is illustrated thatreminder service 515 communicates reminder information to all three ofemail application 520, contacts application 530, and calendarapplication 540. However, it may be appreciated that fewer than allthree may be supplied with the reminder information.

In some implementations, an application that receives the reminderinformation may also be capable of replying to the reminder information.For example, an application may provide a user with the ability todismiss or change the status of a triaged email through the userinterface to that application. A follow-up action could be changed fromone action to another, for example, or deleted entirely. In anotherexample, a follow-up action could be marked as complete and a replyprovided by an associated application to reminder service 515. Thecompleted status of the follow-up action may then be provided to auser's mailbox or other email repository in personal information service512.

FIG. 5B illustrates yet another operational scenario 503 in animplementation in which additional applications are capable of receivingreminder information from reminder service 515, but in some instances byway of an application service. In particular, operational scenario 503involves email application 510, email application 520, contactsapplication 530, productivity application 545, personal informationservice 512, reminder service 515, application service 550, and reminderservice 560.

In operational scenario 503, an email is selected for follow-up actionand email application 510 communicates triage information indicative ofthe same to reminder service 515. The triage information may becommunicated directly to reminder service 515 or indirectly throughpersonal information service 512.

Reminder service 515 identifies which other applications are associatedwith the follow-up action indicated by the triage information andcommunicates reminder information to those applications about thetriaged email. In operational scenario 501, it is illustrated thatreminder service 515 communicates reminder information to emailapplication 520 and to contacts application 530. However, reminderservice 515 also communicates reminder information to reminder service560, which resides in application service 550.

Reminder service 560 may be any software application, module, orcomponent capable of receiving reminder information from reminderservice 515. Application service 550 may be any software application,service, module, component, or collections thereof, capable of providinga productivity application service to productivity application 545 andin which reminder service 560 may be hosted. Application service 550 andreminder service 560 may be implemented using any suitable computingsystem or collections of computing systems, of which computing system900 is representative.

Reminder service 560, by way of application service 550, communicatesreminder information to productivity application 545. Productivityapplication 545 may then surface a reminder to a user through a userinterface to application service 550. It may be appreciated that,although reminder information is supplied to all three additionalapplications in operational scenario 503, in some scenarios fewer thanall three may be involved.

In some implementations, an application that receives the reminderinformation may also be capable of replying to the reminder information.For example, an application may provide a user with the ability todismiss or change the status of a triaged email through the userinterface to that application. A follow-up action could be changed fromone action to another, for example, or deleted entirely. In anotherexample, a follow-up action could be marked as complete and a replyprovided by an associated application to reminder service 515. Thecompleted status of the follow-up action may then be provided to auser's mailbox or other email repository in personal information service512.

FIG. 6 illustrates an operational scenario 600 involving a userinterface 601 to an email service. User interface 601 may be rendered byan email application executed by a suitable computing system, of whichcomputing system 900 is representative.

In operation, an initial view in user interface 601 is rendered thatincludes an inbox 610, a filter menu 620, a function menu 630, and amessage preview pane 635. A user may interact with the various featuresand functions of user interface 601 to, for example, read and composeemails and other types of messages and notifications. In addition, auser may triage their email using some of the features and functions ofuser interface 601.

Inbox 610 includes various messages and other items, including email611, email 612, text message 613, email 614, and a notification 615 of amissed phone call. Which items are displayed in inbox 610 may depend onhow it is set to be filtered. In particular, filter menu 620 allows auser to filter items based on how they have been triaged. For example,filter menu 620 includes a control 621 for viewing all emails, a control622 for viewing those selected be read later, a control 623 for viewingthose selected to be replied to later, and a control 624 for performingtriage and picking follow-up actions for any of the items in inbox 610.

Triage may also be performed on an email via function menu 630. Infunction menu 630, various options are available for whichever item isselected for viewing in message preview pane 635. In this scenario,email 614 has been selected and its content is displayed in messagepreview pane 635. Email 614 may be subject to the various controls infunction menu 630, including a control 631 for forwarding an email, acontrol 632 for replying to an email, a control 634 for deleting anemail, and a control 633 for surfacing a triage menu with which email614 may be triaged.

Upon selection of control 633, represented by user input 641, a triagemenu 650 is rendered which various follow-up actions included therein.The follow-up actions include one follow-up action 651 for reading theemail later, a follow-up action 652 for replying to the email later, afollow-up action 653 for scheduling a meeting later, a follow-up action654 for placing a call later, and a follow-up action 655 for textinglater. It may be appreciated that other follow-up actions in addition toor in place of those disclosed herein may be included in triage menu650. In addition, it may be appreciate that triage menu 650 may also berendered in response to a selection of control 624.

FIG. 7 illustrates an operational scenario 700 involving another userinterface 701 to an email service. User interface 701 may be rendered byan email application executed by a suitable computing system, of whichcomputing system 900 is representative.

In operation, an initial view in user interface 701 is rendered thatincludes an inbox 710 and a filter menu 720. A user may interact withthe various features and functions of user interface 701 to, forexample, read and compose emails and other types of messages andnotifications. In addition, a user may triage their email using some ofthe features and functions of user interface 701.

Inbox 610 includes email 711, email 712, text message 713, email 714,email 715, email 716, and email 717. Which items are displayed in inbox710 may depend on how it is set to be filtered. In particular, filtermenu 720 allows a user to filter items based on how they have beentriaged. For example, filter menu 720 includes a control 721 for viewingall emails, a control 722 for viewing those selected be read later, acontrol 723 for viewing those selected for a later phone call, and acontrol 724 for performing triage and picking follow-up actions for anyof the items in inbox 710.

In this scenario, a user input 741 is initiated to select control 723,which triggers inbox 710 to be filtered to only those items for which aphone call is to be placed. Accordingly, user interface 701 is modifiedsuch that only email 712 and email 715 are displayed in inbox 710 asthose two emails were triaged earlier for phone calls.

In some implementations, which filter options are rendered in filtermenu 720 may be dynamically determined. For example, the ability tofilter by emails subject to phone calls may be surfaced in an emailapplication running on a smart phone, but not on some other device thatlacks phone calling capability, or for which phone calls are not a mainfunction. In another example, the ability to filter by emails triagedfor text messaging may not be surfaced on a device that lacks textmessaging capability. Other contextual influences on what options may besurfaced may be considered within the scope of this disclosure.

It may be appreciated that user interface 701 could be considered asubsequent user interface in that a user may triage email using adifferent user interface to the same email service. For example, a usermay triage their email using an email application on one device and theninteract with the triaged email using another email application onanother device. Thus, user interface 701 may be considered a subsequentuser interface because a user may have used a different user interfacepreviously.

FIG. 8 illustrates two exemplary user interfaces, including userinterface 801 to a contacts service and user interface 803 to aproductivity service. User interface 801 may be rendered when a contactsapplication is executed by a suitable computing system, of whichcomputing system 900 is representative. User interface 803 may also berendered when a productivity application is executed by a suitablecomputing system. User interface 801 and user interface 803 bothillustrate various ways in which a reminder may be surface to remind auser about an email or other item that has been triaged for follow-upaction.

User interface 801 includes a contacts list 810 in which variouscontacts 811-818 are displayed. User interface 801 also includesreminder 822 and reminder 824 that are surfaced to remind a user about atriaged item. Reminder 822 may be a graphical element that reminds auser an email and is displayed in visual association with contact 812.In some implementations, the visual association may be driven by alogical association between the triaged email and a contact, such aswhen a participant in the email is the contact. For example, an emailfrom a sender may be triaged for later follow-up action. A reminder thatis then rendered for the email can be displayed in visual associationwith the contact for the sender so that, when a user is browsingcontacts list 810, he or she is reminded of the email. Reminder 824 mayalso be visually associated with contact 814 so as to remind a userabout an email involving a person associated with contact 814. Othertypes of reminders and other ways in which to visually present thereminders are possible and may be considered within the scope of thepresent disclosure.

User interface 803 includes a productivity application menu 830 in whichvarious features and functions of a productivity application or servicemay be made available. User interface 803 also includes a most recentlyused menu 840 and a template canvas 850. The view presented by userinterface 803 may be one that is encountered by a user when initiallylaunching a productivity application, for instance.

Most recently used menu 840 includes representations 841-845 of variousdocuments that were used recently. Template canvas 850 includes varioustemplate documents 851-856 from which a user may select a template whencreating a document. User interface 803 also includes a reminder 861surfaced in visual proximity to a representation 842 of a document andreminder 863 surfaced in visual proximity to another representation 845of a document.

Reminder 861 and reminder 863 may each be a graphical element thatreminds a user about an email that may be associated with a documentrepresented in most recently used menu 840. For example, an email may betriaged for later reading that includes an attachment. The attachmentcan be surfaced as a document in the most recently used menu 840. Inanother example, an email triaged for later reading may have been sentby a person that created, modified, or is somehow else related to one ofthe documents represented in most recently used menu 840. As such areminder about the email can be surfaced nearby a representation of thatdocument. Other types of reminders and other ways in which to visuallypresent the reminders in a most recently used menu are possible and maybe considered within the scope of the present disclosure. It may also beappreciated that reminders could be surfaced in a user interface to aproductivity application service in other ways, such as in other menus,on template canvas 850, or elsewhere.

FIG. 9 illustrates computing system 900, which is representative of anysuitable computing system or collection of systems that may be employedto implement all or portions of a reminder service 910. Examples ofreminder service 910 include reminder service 115 and reminder service515.

Examples of computing system 900 include server computers, rack servers,web servers, cloud computing platforms, and data center equipment, aswell as any other type of physical or virtual server machine, and anyvariation or combination thereof. In some implementations, a collectionof multiple computing systems may be employed to implement all orportions of a collaboration service which may be hosted in one or moredata centers, virtual data centers, or any other suitable computingfacilities.

Computing system 900 is also representative of any suitable computingsystem or collection of systems that may be employed to implement all orportions of an email application 911, or any other application. Examplesof email application 911 include but are not limited to emailapplication 110, email application 510, and email application 520, aswell as any other email application. Computing system 900 is alsorepresentative of any computing system suitable for implementing any ofthe user interfaces 111, 601, 701, 801, and 803, as well as any otheruser interface. Examples of computing system 900 also include, but arenot limited to, desktop computers, laptop computers, tablet computers,notebook computers, mobile computing devices, smart phones, cell phones,media devices, and gaming devices, as well as any other type of physicalor virtual computing machine.

Computing system 900 may be implemented as a single apparatus, system,or device or may be implemented in a distributed manner as multipleapparatuses, systems, or devices. Computing system 900 includes, but isnot limited to, processing system 901, storage system 903, software 905,communication interface system 907, and user interface system 909.Processing system 901 is operatively coupled with storage system 903,communication interface system 907, and user interface system 909. Userinterface system 909 is optional in some implementations. Processingsystem 901 loads and executes software 905 from storage system 903. Whenexecuted by processing system 901, software 905 directs processingsystem 901 to operate as described herein for any one or more ofreminder services 115 and 515, as well as email applications 110, 510,and 520, and optionally as described for any of the user interfaces andoperational scenarios and sequences disclosed herein. Computing system900 may optionally include additional devices, features, orfunctionality not discussed for purposes of brevity.

Referring still to FIG. 9, processing system 901 may comprise amicroprocessor and other circuitry that retrieves and executes software905 from storage system 903. Processing system 901 may be implementedwithin a single processing device but may also be distributed acrossmultiple processing devices or sub-systems that cooperate in executingprogram instructions. Examples of processing system 901 include generalpurpose central processing units, application specific processors, andlogic devices, as well as any other type of processing device,combinations, or variations thereof.

Storage system 903 may comprise any computer readable storage mediareadable by processing system 901 and capable of storing software 905.Storage system 903 may include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data. Examples of storage media include randomaccess memory, read only memory, magnetic disks, optical disks, flashmemory, virtual memory and non-virtual memory, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other suitable storage media. In no case is the computer readablestorage media a propagated signal.

In addition to computer readable storage media, in some implementationsstorage system 903 may also include computer readable communicationmedia over which software 905 may be communicated internally orexternally. Storage system 903 may be implemented as a single storagedevice but may also be implemented across multiple storage devices orsub-systems co-located or distributed relative to each other. Storagesystem 903 may comprise additional elements, such as a controller,capable of communicating with processing system 901 or possibly othersystems.

Software 905 may be implemented in program instructions and among otherfunctions may, when executed by processing system 901, direct processingsystem 901 to operate as described herein as described with respect tothe various operational scenarios disclosed herein. In particular, theprogram instructions may include various components or modules thatcooperate or otherwise interact to carry out the various processes andoperational scenarios described herein. The various components ormodules may be embodied in compiled or interpreted instructions or insome other variation or combination of instructions. The variouscomponents or modules may be executed in a synchronous or asynchronousmanner, serially or in parallel, in a single threaded environment ormulti-threaded, or in accordance with any other suitable executionparadigm, variation, or combination thereof. Software 905 may includeadditional processes, programs, or components, such as operating systemsoftware or other application software. Software 905 may also comprisefirmware or some other form of machine-readable processing instructionsexecutable by processing system 901.

In general, software 905 may, when loaded into processing system 901 andexecuted, transform a suitable apparatus, system, or device (of whichcomputing system 900 is representative) overall from a general-purposecomputing system into a special-purpose computing system customized tofacilitate enhanced email triage as described herein for eachimplementation. Indeed, encoding software 905 on storage system 903 maytransform the physical structure of storage system 903. The specifictransformation of the physical structure may depend on various factorsin different implementations of this description. Examples of suchfactors may include, but are not limited, to the technology used toimplement the storage media of storage system 903 and whether thecomputer-storage media are characterized as primary or secondarystorage, as well as other factors.

For example, if the computer readable storage media are implemented assemiconductor-based memory, software 905 may transform the physicalstate of the semiconductor memory when the program instructions areencoded therein, such as by transforming the state of transistors,capacitors, or other discrete circuit elements constituting thesemiconductor memory. A similar transformation may occur with respect tomagnetic or optical media. Other transformations of physical media arepossible without departing from the scope of the present description,with the foregoing examples provided only to facilitate the presentdiscussion.

Referring again to FIG. 1 as an example, through the operation of acomputing system or systems of which computing system 900 isrepresentative, transformations may be performed with respect to a userinterface to an email service, such as user interface 111 and userinterface 121. As an example, a user may select an email for triage inuser interface 111. Accordingly, a reminder is surfaced in userinterface 121, thereby changing the state of user interface 121 from afirst state (without the reminder) to a second, transformed state (withthe reminder). Other examples of transformations are possible and may beconsidered within the scope of the present disclosure.

It should be understood that computing system 900 is generally intendedto represent a computing system or systems on which software 905 may bedeployed and executed in order to implement enhanced email triage.However, computing system 900 may also be suitable as any computingsystem on which software 905 may be staged and from where software 905may be distributed, transported, downloaded, or otherwise provided toyet another computing system for deployment and execution, or yetadditional distribution.

Communication interface system 907 may include communication connectionsand devices that allow for communication with other computing systems(not shown) over a communication network or collection of networks (notshown). Examples of connections and devices that together allow forinter-system communication may include network interface cards,antennas, power amplifiers, RF circuitry, transceivers, and othercommunication circuitry. The connections and devices may communicateover communication media to exchange communications with other computingsystems or networks of systems, such as metal, glass, air, or any othersuitable communication media. The aforementioned media, connections, anddevices are well known and need not be discussed at length here.

Communication between computing system 900 and any other computingsystem (not shown) may occur over a communication network or networksand in accordance with various communication protocols, combinations ofprotocols, or variations thereof. Examples of communication networksover which computing system 900 may exchange information with othercomputing systems include intranets, the Internet, local area networks,wide area networks, wireless networks, wired networks, virtual networks,software defined networks, data center buses, computing backplanes,networks, or any combination or variation thereof. The aforementionedcommunication networks and protocols are well known and need not bediscussed at length here. However, some communication protocols that maybe used include, but are not limited to, the Internet protocol (IP,IPv4, IPv6, etc.), the transfer control protocol (TCP), and the userdatagram protocol (UDP), as well as any other suitable communicationprotocol, variation, or combination thereof. In any of theaforementioned examples in which information is exchanged, the exchangeof information may occur in accordance with any of a variety ofprotocols, including FTP (file transfer protocol), HTTP (hypertexttransfer protocol), REST (representational state transfer), WebSocket,DOM (Document Object Model), HTML (hypertext markup language), CSS(cascading style sheets), HTML5, XML (extensible markup language),JavaScript, JSON (JavaScript Object Notation), and AJAX (AsynchronousJavaScript and XML), as well as any other suitable protocol, variation,or combination thereof.

User interface system 909 may include a keyboard, a mouse, a voice inputdevice, a touch input device for receiving a touch gesture from a user,a motion input device for detecting non-touch gestures and other motionsby a user, and other comparable input devices and associated processingelements capable of receiving user input from a user. Output devicessuch as a display, speakers, haptic devices, and other types of outputdevices may also be included in user interface system 909. In somecases, the input and output devices may be combined in a single device,such as a display capable of displaying images and receiving touchgestures. The aforementioned user input and output devices are wellknown in the art and need not be discussed at length here.

User interface system 909 may also include associated user interfacesoftware executable by processing system 901 in support of the varioususer input and output devices discussed above. Separately or inconjunction with each other and other hardware and software elements,the user interface software and user interface devices may support agraphical user interface, a natural user interface, or any other type ofuser interface. For example, user interface 111 or user interface 121may be presented through user interface system 909. In addition, userinput made with respect to user interface 111 or user interface 121 canbe input via user interface system 909.

The functional block diagrams, operational scenarios and sequences, andflow diagrams provided in the Figures are representative of exemplarysystems, environments, and methodologies for performing novel aspects ofthe disclosure. While, for purposes of simplicity of explanation,methods included herein may be in the form of a functional diagram,operational scenario or sequence, or flow diagram, and may be describedas a series of acts, it is to be understood and appreciated that themethods are not limited by the order of acts, as some acts may, inaccordance therewith, occur in a different order and/or concurrentlywith other acts from that shown and described herein. For example, thoseskilled in the art will understand and appreciate that a method couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, not all acts illustratedin a methodology may be required for a novel implementation.

The included descriptions and figures depict specific implementations toteach those skilled in the art how to make and use the best option. Forthe purpose of teaching inventive principles, some conventional aspectshave been simplified or omitted. Those skilled in the art willappreciate variations from these implementations that fall within thescope of the invention. Those skilled in the art will also appreciatethat the features described above can be combined in various ways toform multiple implementations. As a result, the invention is not limitedto the specific implementations described above, but only by the claimsand their equivalents.

What is claimed is:
 1. A method for operating a computing system tofacilitate rendering an email application on a display system, themethod comprising: in a user interface of an email application,rendering an option to triage an email; in response to a selection ofthe option to triage the email, rendering a triage menu in the userinterface of the email application that comprises a plurality of triageactions, wherein at least one triage action of the plurality of triageactions indicates a follow-up action and corresponds to a differentapplication in which to perform the follow-up action; and in response toa selection of the one triage action, communicating triage informationindicative of the selection of the one triage action to a reminderservice that communicates to the different application, reminderinformation indicative of the follow-up action and the email.
 2. Themethod of claim 1 wherein the plurality of triage actions comprises oneor more of reading the email later, replying to the email later, placinga call related to the email later, and scheduling a meeting related tothe email.
 3. The method of claim 1 wherein the one triage actionfurther corresponds to another application that is distinguished fromthe email application and the different application and wherein.
 4. Themethod of claim 3 wherein the reminder service further communicates tothe other application the reminder information.
 5. The method of claim 1wherein the different application comprises one of a real-timecommunication application, a contacts application, a calendarapplication, a productivity application, a gaming application, and anadditional email application.
 6. The method of claim 1 furthercomprising rendering a user interface to the different application,wherein the user interface to the different application includes areminder rendered based on the reminder information.
 7. The method ofclaim 6 further comprising a display system displaying the reminder asat least one of a text, a graphical element, and a visual reminder. 8.An apparatus comprising: one or more computer readable storage mediahaving program instructions stored thereon that, when executed by aprocessing system, direct the processing system to at least: in a userinterface of an email application, render an option to triage an email;in response to a selection of the option to triage the email, render atriage menu in the user interface of the email application thatcomprises a plurality of triage actions, wherein at least one triageaction of the plurality of triage actions indicates a follow-up actionand corresponds to a different application in which to perform thefollow-up action; and in response to a selection of the one triageaction, communicate triage information indicative of the selection ofthe one triage action to a reminder service that communicates to thedifferent application, reminder information indicative of the follow-upaction and the email.
 9. The apparatus of claim 8 wherein the pluralityof triage actions comprises one or more of reading the email later,replying to the email later, placing a call related to the email later,and scheduling a meeting related to the email.
 10. The apparatus ofclaim 8 wherein the one triage action further corresponds to anotherapplication that is distinguished from the email application and thedifferent application.
 11. The apparatus of claim 10 wherein thereminder service further communicates to the other application thereminder information.
 12. The apparatus of claim 8 wherein the differentapplication comprises one of a real-time communication application, acontacts application, a calendar application, a productivityapplication, a gaming application, and an additional email application.13. The apparatus of claim 8 wherein the program instructions furtherdirect the processing system to render a user interface to the differentapplication, wherein the user interface to the different applicationincludes a reminder rendered based on the reminder information.
 14. Theapparatus of claim 13 wherein the program instructions further directthe processing system to display the reminder as at least one of a text,a graphical element, and a visual reminder.
 15. One or morecomputer-readable storage media having program instructions storedthereon to facilitate rendering an email application on a displaysystem, wherein the program instructions, when executed by a computingsystem, direct the computing system to at least: in a user interface ofan email application, render an option to triage an email; in responseto a selection of the option to triage the email, render a triage menuin the user interface of the email application that comprises aplurality of triage actions, wherein at least one triage action of theplurality of triage actions indicates a follow-up action and correspondsto a different application in which to perform the follow-up action; andin response to a selection of the one triage action, communicate triageinformation indicative of the selection of the one triage action to areminder service that communicates to the different application,reminder information indicative of the follow-up action and the email.16. The one or more computer-readable storage media of claim 15 whereinthe plurality of triage actions comprises one or more of reading theemail later, replying to the email later, placing a call related to theemail later, and scheduling a meeting related to the email.
 17. The oneor more computer-readable storage media of claim 15 wherein the onetriage action further corresponds to another application that isdistinguished from the email application and the different applicationand wherein.
 18. The one or more computer-readable storage media ofclaim 17 wherein the reminder service further communicates to the otherapplication the reminder information.
 19. The one or morecomputer-readable storage media of claim 15 wherein the differentapplication comprises one of a real-time communication application, acontacts application, a calendar application, a productivityapplication, a gaming application, and an additional email application.20. The one or more computer-readable storage media of claim 15 whereinthe program instructions further direct the computing system to render auser interface to the different application, wherein the user interfaceto the different application includes a reminder rendered based on thereminder information.